Fetch ReferenceItem content from raw GitHub URLs when possible
#168
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lisad
approved these changes
Jan 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #166.
Most of the selection between GitHub raw and repo URLs was actually implemented in #167. However, our schema methods were still just fetching whatever was at the
Referenceitem's URL as provided when rendering content. This PR changes a couple things:ReferenceItemis provided by GitHub, and if so, fetches from the raw URL if available.This ensures that when we attempt to fetch content from files hosted on GitHub (like READMEs or schema specs), we can hopefully get the actual file content even if the user only provided us with a link to GitHub's webpage for the file.